fix(agents): document read-only constraint in researcher agent#180
fix(agents): document read-only constraint in researcher agent#180maystudios merged 1 commit intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds explicit documentation to the researcher agent template clarifying its read-only constraints and how outputs should be returned to the orchestrator-driven workflow.
Changes:
- Adds a new Constraints section describing the researcher as read-only (no Write/Edit tools).
- States that researcher outputs are returned via the handoff contract rather than written to disk.
- Mentions how GitHub writes are performed (via
Bash+gh).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Constraints | ||
|
|
||
| - **Read-only operation** — You do NOT have Write or Edit tools. You cannot create or modify files. | ||
| - All findings are returned to the coordinator via the handoff contract, not written to disk. |
There was a problem hiding this comment.
Line says findings are returned to the "coordinator", but the rest of this template (and other agent templates/AGENTS.md) consistently refer to the "orchestrator" as the mediator of handoffs. Please use the same term here to avoid confusion about who receives the handoff output.
| - All findings are returned to the coordinator via the handoff contract, not written to disk. | |
| - All findings are returned to the orchestrator via the handoff contract, not written to disk. |
|
|
||
| - **Read-only operation** — You do NOT have Write or Edit tools. You cannot create or modify files. | ||
| - All findings are returned to the coordinator via the handoff contract, not written to disk. | ||
| - GitHub writes (issue comments, labels, etc.) go through `Bash` with `gh` CLI commands, not through file writes. |
There was a problem hiding this comment.
The constraints section says GitHub writes go through Bash/gh, but in this repo the orchestrator is documented as the component that posts agent outputs to GitHub after parsing the handoff contract (see templates/agents/AGENTS.md). In this researcher-specific constraints section, consider clarifying that the researcher should return findings via the handoff contract and let the orchestrator handle GitHub posting, rather than implying the researcher should perform GitHub writes directly.
| - GitHub writes (issue comments, labels, etc.) go through `Bash` with `gh` CLI commands, not through file writes. | |
| - You do not perform GitHub writes yourself. Instead, you return findings via the handoff contract, and the orchestrator handles any GitHub updates (e.g., via `Bash` with `gh` CLI commands), not through file writes. |
|
🎉 This PR is included in version 5.13.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
## Constraintssection totemplates/agents/researcher.mdexplicitly documenting that the researcher agent operates in read-only mode (no Write or Edit tools).BashwithghCLI commands.Test plan
🤖 Generated with Claude Code